feat: add pg_cron container image#143
Conversation
pg_cron is an open-source extension that provides a simple cron-based job scheduler for PostgreSQL, allowing you to schedule PostgreSQL commands directly from the database. Closes cloudnative-pg#139 Signed-off-by: Jeremy Schneider <schneider@ardentperf.com>
|
Hi @ardentperf, now that we've resolved the version issue, could you please revisit your initial attempt? Let me know your thoughts, or we may need to close this PR since it has significantly diverged from the main branch, and it might be better/easier to submit a new one. |
|
@ardentperf, are you willing to contribute to this PR? Otherwise, I am closing this, as it has drifted a lot from the current specification. Thanks. |
updated to post-cloudnative-pg#149/cloudnative-pg#154 metadata format: nested version objects with package+sql versions, set cron.database_name so CREATE EXTENSION works during E2E tests, enables create_extension Signed-off-by: Jeremy Schneider <schneider@ardentperf.com>
|
Can a disclaimer be added for the pg_cron extension? It should indicate that writable workloads will be executed locally on the primary instance, bypassing the service. In the event of a network partition or if the primary instance becomes isolated, these workloads will continue to write on the primary until it self-fences. It’s important to warn users about this. |
|
My own view is that CNPG should move toward making synchronous replication the default configuration (cf. cloudnative-pg/cloudnative-pg#10783 ) and Kubernetes Services are a traffic routing mechanism, but IMO we shouldn't generally think of services as a fencing mechanism - they aren't intended for that. |
2 participants
pg_cron is an open-source extension that provides a simple cron-based job scheduler for PostgreSQL, allowing you to schedule PostgreSQL commands directly from the database.
Closes #139